Implements comprehensive FML (FHIR Mapping Language) syntax validation endpoint as requested in the issue. This provides developers with detailed syntax error messages including line and column information for debugging FML content without requiring full compilation.

Implementation

The syntax validation leverages the existing FML tokenizer and parser infrastructure from the codebase to provide comprehensive validation with detailed error reporting:

Core Library (packages/fmlrunner)

• Added FmlSyntaxValidationResult, FmlSyntaxError, and FmlSyntaxWarning types
• Implemented validateSyntax() method in FmlCompiler class with comprehensive error detection
• Added validateFmlSyntax() method to main FmlRunner class

REST API (packages/fmlrunner-rest)

• Added POST /api/v1/fml/validate-syntax endpoint
• Returns FHIR-compliant OperationOutcome resources with validation results
• Proper HTTP status codes (200 for valid, 400 for invalid FML)

MCP Interface (packages/fmlrunner-mcp)

• Added validate-fml-syntax tool with JSON schema validation
• Structured response format for programmatic consumption

Features

Detailed Error Detection:

• Empty content validation
• Missing map declaration detection
• Unmatched braces {} and parentheses () detection
• Keyword validation for required FML elements
• Tokenization and parsing error capture

Advanced Features:

• Line and column information for all errors
• Warning system for missing groups and best practices
• Proper handling of single-line (//) and multi-line (/* */) comments
• Structured error codes for programmatic handling

Multiple Interfaces:

• REST API endpoint for web applications
• MCP tool for Model Context Protocol integration
• Core library method for direct usage

Examples

Valid FML Response

{
  "resourceType": "OperationOutcome",
  "issue": [{
    "severity": "information",
    "code": "informational", 
    "diagnostics": "FML syntax is valid"
  }]
}

Invalid FML Response

{
  "resourceType": "OperationOutcome",
  "issue": [{
    "severity": "error",
    "code": "invalid",
    "diagnostics": "FML content must start with a map declaration",
    "location": ["line 1, column 1"]
  }]
}

Testing

Comprehensive test coverage ensures reliability:

• Core Library: 11/11 tests passing covering all validation scenarios
• REST API: 8/8 tests passing with proper HTTP responses
• MCP Interface: Manual testing confirms functionality

All tests verify error detection, warning generation, line/column reporting, and proper handling of edge cases including comments, empty content, and malformed syntax.

The implementation provides exactly what was requested in the issue: "useful error messages when failed" with precise location information to help developers debug their FML syntax issues.

Fixes #[issue_number]

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.